Use config entry title for Avea light#170978
Conversation
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Updates Avea light entity instantiation and naming to be based on the config entry title instead of the bulb-reported name, with corresponding test adjustments.
Changes:
- Pass the config entry into
AveaLightduring setup. - Derive the entity’s
_attr_namefromentry.titleinstead oflight.name. - Simplify the Avea light test by removing the entity registry dependency and adjusting the mocked bulb name.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| tests/components/avea/test_light.py | Updates test fixtures/mocks to align with entity naming changes and removes entity registry usage. |
| homeassistant/components/avea/light.py | Changes AveaLight construction and sets the entity name from the config entry title. |
| """Initialize an AveaLight.""" | ||
| self._light = light | ||
| self._attr_name = light.name | ||
| self._attr_name = entry.title |
There was a problem hiding this comment.
I’m keeping this PR limited to the regression fix for entities being created from the library default name "Unknown". Moving Avea to device/entity naming with device_info would be a broader metadata change and is better handled separately once we have the right device identifiers.
| """Initialize an AveaLight.""" | ||
| self._light = light | ||
| self._attr_name = light.name | ||
| self._attr_name = entry_title |
There was a problem hiding this comment.
I’m keeping entry_title as the source of the entity name here. The config flow already validated and stored the intended title, while the initial library Bulb.name can still be "Unknown", which is the regression this PR fixes.
Proposed change
Use the config entry title for the Avea light entity name instead of the initial
avea.Bulb.namevalue.The Avea library may still expose the default name
Unknownwhen the entity is created, even though the config flow already validated the device and created the config entry with the correct title. This prevents newly configured bulbs from being added aslight.unknownafter discovery/config flow setup.Type of change
Additional information
Checklist
ruff format homeassistant tests)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest.requirements_all.txt.Updated by running
python3 -m script.gen_requirements_all.To help with the load of incoming pull requests: